The Oracle Linux operating system must audit all uses of the create

The Oracle Linux operating system must audit all uses of the create_module syscall.

Overview

Finding ID	Version	Rule ID	IA Controls	Severity
V-221820	OL07-00-030819	SV-221820r833097_rule		Medium

Description
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. Audit records can be generated from various components within the information system (e.g., module or policy filter). Satisfies: SRG-OS-000471-GPOS-00216, SRG-OS-000477-GPOS-00222

Description

Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. Audit records can be generated from various components within the information system (e.g., module or policy filter). Satisfies: SRG-OS-000471-GPOS-00216, SRG-OS-000477-GPOS-00222

STIG	Date
Oracle Linux 7 Security Technical Implementation Guide	2023-06-02

Details

Check Text ( C-36315r833095_chk )
Verify the operating system generates audit records when successful/unsuccessful attempts to use the "create_module" syscall occur. Check the auditing rules in "/etc/audit/audit.rules" with the following command: $ sudo grep -w "create_module" /etc/audit/audit.rules -a always,exit -F arch=b32 -S create_module -F auid>=1000 -F auid!=unset -k module-change -a always,exit -F arch=b64 -S create_module -F auid>=1000 -F auid!=unset -k module-change If both the "b32" and "b64" audit rules are not defined for "create_module" syscall, this is a finding.

Check Text ( C-36315r833095_chk )

Verify the operating system generates audit records when successful/unsuccessful attempts to use the "create_module" syscall occur.

Check the auditing rules in "/etc/audit/audit.rules" with the following command:

$ sudo grep -w "create_module" /etc/audit/audit.rules

-a always,exit -F arch=b32 -S create_module -F auid>=1000 -F auid!=unset -k module-change

-a always,exit -F arch=b64 -S create_module -F auid>=1000 -F auid!=unset -k module-change

If both the "b32" and "b64" audit rules are not defined for "create_module" syscall, this is a finding.

Fix Text (F-36279r833096_fix)
Configure the operating system to generate audit records when successful/unsuccessful attempts to use the "create_module" syscall occur. Add or update the following rules in "/etc/audit/rules.d/audit.rules": -a always,exit -F arch=b32 -S create_module -F auid>=1000 -F auid!=unset -k module-change -a always,exit -F arch=b64 -S create_module -F auid>=1000 -F auid!=unset -k module-change The audit daemon must be restarted for the changes to take effect.

Fix Text (F-36279r833096_fix)

Configure the operating system to generate audit records when successful/unsuccessful attempts to use the "create_module" syscall occur.

Add or update the following rules in "/etc/audit/rules.d/audit.rules":

-a always,exit -F arch=b32 -S create_module -F auid>=1000 -F auid!=unset -k module-change

-a always,exit -F arch=b64 -S create_module -F auid>=1000 -F auid!=unset -k module-change

The audit daemon must be restarted for the changes to take effect.